-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle Expired TWAP and not started TWAP #153
Conversation
CLA Assistant Lite bot: I have read the CLA Document and I hereby sign the CLA You can retrigger this bot by commenting recheck in this Pull Request |
Removed dependencies detected. Learn more about Socket for GitHub ↗︎ 🚮 Removed packages: @cowprotocol/[email protected] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice. Only some nits about assertions / typos.
de95d05
to
9f59dde
Compare
9f59dde
to
4a11e0f
Compare
Merging as this is already too big. Lets keep iterating |
This PR
Includes some optional blockInfo params
This params allow the
poll
method to use either theblockNumber
or theblockTimestamp
to validate the concrete Conditional Order.Validate start time
It will check if the order started. If it haven't then we can signal we don't want to re-check until the start time
Handle Expired TWAPs
This is causing a lot of noise in the logs. Expired TWAP orders are never deleted. Now they are
Tried it in WatchTower (adapted it in cowprotocol/watch-tower#16)
Don't fail to handle errors
Handled errors should not show as errors
Not included
Left some notes for a future PR on something that will help to reduce significantly the number of checks we need to do.
It's out of scope cause is not a trivial change. It will need a model update in watch tower